This is a dead link. Default branch on this repo is main. Please verify all links in the documentation are still live.

Good catch — the repo's default branch is main, and le-utils uses the same. Fixed this link and every other le-utils/blob/master/... reference across the docs (7 total: nodes.md, files.md, languages.md, csv_metadata/csv_exercises.md, concepts/developer_workflows.md, tutorial/explanations.md) to point at main. Also re-ran the full Sphinx build to confirm no other broken cross-references were introduced.

It has been reported that the tutorial videos are no longer publicly accessible. We should remove any references to them.

Confirmed — the archive.org item backing the tutorial's example video (RiceChef) 404s. Replaced the uri in examples/tutorial/sushichef.py with a live, similarly-small archive.org video (CM_National_Rice_Cooker_1982.mp4, ~1.5MB, already referenced elsewhere in these docs in video_compression.md) and verified the chef still imports and constructs its tree cleanly. tutorial.rst's prose itself didn't reference the URL directly, so no further text change was needed there.

I think it's worth mentioning how to automatically get subtitles from a youtube URL using the ContentNode approach?

Added an example right after the YouTubeSubtitleFile paragraph pairing it with the ContentNode(uri=...) approach — passing a YouTube URL as uri downloads the video, and YouTubeSubtitleFile(youtube_id=..., language=...) fetches the caption track directly from YouTube (confirmed via the pipeline code that this is not automatic from uri alone — it requires the explicit add_file call, same as the local-file SubtitleFile case, just without needing a local .vtt).

Let's add that it's generally recommended to add thumbnails using the "thumbnail" attribute on ContentNode - adding as a separate file is mostly unnecessary.

Added a note recommending ContentNode(..., thumbnail="path/or/url") (also works on ChannelNode/TopicNode) over constructing a standalone ThumbnailFile — confirmed thumbnail accepts the same local path or URL and wraps it in a ThumbnailFile internally via set_thumbnail().

Does the ContentNode URI path also automatically set the language on the file? If it isn't doing that would be good to fix that concurrently with this documentation update.

Good catch — it wasn't. Fixed in ricecooker/classes/nodes.py: ContentNode._process_uri now does metadata_dict.setdefault("language", self.language) before constructing the File object, so a file built from uri inherits the node's language unless the pipeline itself set one explicitly (e.g. a YouTube subtitle track keeps its own per-language code from YoutubeDownloadHandler). Added test_automatic_resource_node_document_inherits_node_language in tests/test_tree.py covering the inheritance case, and a sentence in docs/tutorial/explanations.md noting it. Verified with uv run --group test pytest.

This video isn't available.

Confirmed — removed the whole "Video overview" section (prose link + iframe) from docs/tutorial/gettingstarted.rst rather than swapping in another dead/unverifiable link, since there's no known-good replacement for this one. The rest of the getting-started walkthrough doesn't depend on it.

This wasn't what I meant. You can pass "subtitle_languages" to the pipeline context to automatically trigger subtitle download from YouTube: https://github.com/learningequality/ricecooker/blob/main/ricecooker/utils/pipeline/transfer.py#L192

Ah, got it — replaced the YouTubeSubtitleFile.add_file(...) example with ContentNode(uri=..., context={"subtitle_languages": ["en", "es"]}), which is what actually triggers automatic subtitle download from YouTube on the uri path (confirmed against YoutubeDownloadHandler.get_file_kwargs in ricecooker/utils/pipeline/transfer.py:180-205, which loops over context.subtitle_languages to fetch a caption track per language). Linked directly to that handler in the doc so the mechanism is traceable.